| Purpose |
EMEA SEPA direct debit for customers |
| Requested By |
Jingsha/Baiwa |
| Spec Created By |
Raghav |
| Spec Created Date |
06/08/2016 |
| Spec QA by |
Raghav |
| Objects |
ZFI_DMEE_EXIT PAYMZSEPA_DD VC_TFPM042F VC_T012 VC_T042ZL V_T042E VC_BANKDET VC_TFPM042FC |
| Document Status |
Wip |
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
30 |
| 2 |
Documentation |
10 |
| 3 |
Development/ Config |
30 |
| 4 |
Unit test in DEV |
25 |
| 5 |
Unit test in QUA |
15 |
| 6 |
Other activity |
|
| TOTAL |
110 |
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
| 1 |
Removal of fields optional fields cd, cd and Ustrd |
Baiwa |
11/21/2016 |
|
| 2 |
Optional fields deletion in XML file |
Baiwa |
11/27/2016 |
|
| 3 |
Add file name cocd_yyyymmddhhss |
Baiwa |
01/10/2017 |
|
| 4 |
Change the field CrdtSchmID as NEC company info and add the file name |
Baiwa |
01/20/2017 |
|
| 5 |
Update the fields CtgyPurp, DbtrAcct with SUPP and remove the field RmtInfo from file |
Baiwa |
02/07/2017 |
|
| 6 |
Change the fields Orgid, Prvtid and Ctry IC to ES |
Baiwa |
03/18/2018 |
| File Name |
Field Identifier |
Field Logic |
Field description |
Given points in SEPA file |
| One record per file |
||||
| GrpHdr |
MsgId |
FPAYHX-RENUM |
Reference Number from SAP |
1.1 Point to point reference assigned by the instructing party and sent to the next party in the chain to unambiguously identify the message |
| CreDtTm |
YYYY-MM-DDTTime |
YYYY-MM-DDTTime |
1.2 Date and time at which a (group of) payment instruction(s) was created by the instructing party YYYY-MM-DDThh:mm:ss |
|
| NbOfTxs |
Ref TX = 2(no of count) |
Number of count of customers in file |
1.6 Number of individual transactions contained in the message |
|
| CtrlSum |
Ref IA = 1(sum of value) |
Sum of total amount |
1.7 Total of all individual amounts included in the message, irrespective of currencies |
|
| Nm |
FPAYHX-NAMEZ |
Company code name |
1.8 Party initiating the payment. In the Direct Debit context, this can be the creditor, or the party that initiates the payment on behalf of the creditor |
|
| Id |
GB63ZZZSDDBARC0000004599312 |
Constant Value |
1.8 Identification ESDDSSSNNNNNNNNN |
|
| PmtInf |
Have multiple lines |
|||
| PmtInfId |
FPAYHX-RENUM |
Reference Number from SAP |
2.1 Reference assigned by a sending party to unambiguously identify the payment information block within the message |
|
| PmtMtd |
DD |
Constant Value |
2.2 Specifies the means of payment that will be used to move the amount of money DD=Direct Debit |
|
| NbOfTxs |
Ref TX = 2(no of count) |
Number of count of customers in file |
2.4 Number of individual transactions contained in the payment block |
|
| CtrlSum |
Ref IA = 1(sum of value) |
Sum of total amount |
2.5 Total of all individual amounts included in the payment block, irrespective of currencies |
|
| One record per file |
||||
| PmtTpInf |
Cd |
SEPA |
2.9 Identification of a pre-agreed level of service between the parties in a coded form SEPA |
|
| Cd4 |
CORE or B2B condition |
Will reflect always CORE |
2.12 User community specific instrument “CORE” or “B2B” |
|
| SeqTp |
RCUR |
Constant Value for Now |
2.14 Identifies the Direct Debit sequence, e.g. first, recurrent, final or one-off "FRST" "RCUR" "FNAL" or "OOFF" |
|
| Cd |
2.15 Specifies the high level purpose of the instruction based on a set of pre-defined categories |
|||
| ReqdColltnDt |
FPAYH-AUSFD |
Run Date |
2.18 Date at which the creditor requests the amount of money to be collected from the debtor YYYY-MM-DD |
|
| Cdtr |
Nm |
FPAYHX-NAMEZ |
Company Name |
2.19 Party to which an amount of money is due |
| Ctry |
FPAYHX-LAND1 |
Country |
2.19 Country is check against the list of country names obtain from the United Nations (ISO 3166, Alpha-2 code) |
|
| AdrLine |
Address line1 |
2.19 Street and Building Number |
||
| AdrLine |
City |
2.19 Postal code and Town |
||
| CdtrAcct |
IBAN |
FPAYHX-UIBAN |
Company IBAN |
2.20 Unambiguous identification of the account of the creditor to which a credit entry will be posted as a result of the payment transaction IBAN-format |
| CdtrAgt |
BIC |
FPAYHX-USWIF |
Company SWIFT |
2.21 Financial institution servicing an account for the creditor CAIXESBBXXX (2.21) |
| ChrgBr |
ChrgBr |
SLEV |
Constant Value |
2.24 Specifies which party/parties will bear the charges associated with the processing of the payment transaction “SLEV” (2.24) |
| CdtrSchmeId |
Id |
GB63ZZZSDDBARC0000004599312 |
Debtor Number |
2.27 Credit party that signs the Direct Debit mandate |
| Prtry |
SEPA |
Constant Value |
2.27 “SEPA” |
|
| One complete record with in the file(Customer Info) |
||||
| DrctDbtTxInf |
EndToEndId |
FPAYH-KOINH |
Customer Name |
2.31 Unique identification assigned by the initiating party to unambiguously identify the transaction |
| InstdAmt |
FPAYH-RWBTR |
Customer Due amount |
2.44 Amount of the Direct Debit, expressed in euro |
|
| Ccy |
FPAYHX-WAERS |
Currency key |
EUR |
|
| MndtId |
FPAYH-GPA1R |
Customer Number |
2.48 Reference of the Direct Debit mandate that has been signed between the debtor and the creditor |
|
| DtOfSgntr |
2009-10-31 |
Constant Value |
2.49 Date on which the Direct Debit mandate has been signed by the debtor YYYY-MM-DD |
|
| BIC |
FPAYH-ZSWIF |
Customer SWIFT code |
2.70 Financial institution servicing an account for the debtor |
|
| Nm |
FPAYH-KOINH |
Account Holder Name |
2.72 Party that owes an amount of money to the (ultimate) creditor |
|
| Ctry |
FPAYHX-ZLISO and if IC then ES |
Country ISO code |
2.72 Country is check against the list of country names obtain from the United Nations (ISO 3166, Alpha-2 code) |
|
| AdrLine |
FPAYHX-ZPFST |
P.O. Box or Street for Postal Code/City |
2.72 Street and Building number |
|
| AdrLine |
FPAYHX-ZPLOR |
Postal Code/City of the Payee's Display Field |
2.72 Postcode and Town |
|
| IBAN |
FPAYH-ZIBAN |
Customer IBAN |
2.73 Identification of the account of the debtor to which a debit entry will be made to execute the transfer IBAN-format |
|
| Cd |
Not Mandatory |
2.77 Specifies the underlying reason of the payment transaction |
||
| Ustrd |
Not Mandatory |
2.89 Information supplied so as to enable the matching of an entry with the items the transfer is supposed to settle, e.g. a commercial invoice, in an unstructured form |
||
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
Automatic payment run for the for cocd 0030 for incoming payments |
APP should generate xml file with the fixed length and all mantade fields |
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
APP run for cocd 0030 to generate new SEPA xml file for customers with deletion of optional fieds |
SEPA XML file should generate without the optional fields cd, cd and Ustrd |
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
APP run for customers with single collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with constant CdtrSchmeId GB98ZZZSDDBARC0000004599312 and file name with format _cocd_yyyymmddhhss |
| FI-002 |
APP run for customers with multiple collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with constant CdtrSchmeId GB98ZZZSDDBARC0000004599312 for every collection dateand file name with format _cocd_yyyymmddhhss |
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
APP run for customers with single collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with below changes 1. CtgyPurp with SUPP 2. DbtrAcct with SUPP 3. RmtInfo should not be in XML file |
| FI-002 |
APP run for customers with multiple collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with below changes 1. CtgyPurp with SUPP 2. DbtrAcct with SUPP 3. RmtInfo should not be in XML file |
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
APP run for customers with single collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with below changes 1. CtgyPurp with SUPP 2. DbtrAcct with SUPP |
| FI-002 |
APP run for customers with multiple collection date to generate SEPA xml for cocd0030 |
SEPA XML file should generate with below changes 1. CtgyPurp with SUPP 2. DbtrAcct with SUPP |
| Test ID |
Test Scenario |
Expected Results |
| FI-001 |
EMEA SEPA File generation with IC Customer |
File should replace country code IC to ES and fileds Orgid and Prvtid value should be 'GB63ZZZSDDBARC0000004599312' |
| FI-002 |
EMEA SEPA File generation with multiple Customers |
File should replace country code IC to ES and fileds Orgid and Prvtid value should be 'GB63ZZZSDDBARC0000004599312' |